feat(slack): Add frontend pipeline step for Slack integration setup#112417
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 65b70bf. Configure here.
| popup={{height: 900}} | ||
| /> | ||
| ); | ||
| } |
There was a problem hiding this comment.
New OAuth step duplicates existing GitLab implementation
Low Severity
SlackOAuthLoginStep is nearly identical to GitLabOAuthLoginStep in pipelineIntegrationGitLab.tsx — same type signature, same handleOAuthCallback body, same OAuthLoginStep rendering — differing only in serviceName and the popup option. As more OAuth-only integrations are added, this boilerplate will keep getting copied. A small shared factory (parameterized by serviceName and optional PopupOptions) would eliminate the duplication.
Reviewed by Cursor Bugbot for commit 65b70bf. Configure here.
Register the Slack integration in the pipeline registry with a single OAuthLoginStep component. This is the simplest integration frontend since Slack only requires an OAuth authorization flow with no additional configuration steps. Ref [VDY-42](https://linear.app/getsentry/issue/VDY-42/slack-api-driven-integration-setup)
65b70bf to
aaa5747
Compare
…112417) Register the Slack integration in the pipeline registry with a single OAuthLoginStep component. This is the simplest integration frontend since Slack only requires an OAuth authorization flow with no additional configuration steps. Ref [VDY-42](https://linear.app/getsentry/issue/VDY-42/slack-api-driven-integration-setup)


Register the Slack integration in the pipeline registry with a single
OAuthLoginStep component. This is the simplest integration frontend since
Slack only requires an OAuth authorization flow with no additional
configuration steps.
Ref VDY-42